Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 0a91819fd3e1a8dcb7842881b115030ec184ad4ff6ce2040b5b86a6b5ef4197b

Tx prefix hash: 0ca0db8355ede78e7cd549edee323adecde11e387d1291c13a08cf8cb1fc155f
Tx public key: 8f2a45663f4880af59f26b8d823ffece5c2a44d1dade0fc99c39961f695fa1d8
Timestamp: 1734712030 Timestamp [UCT]: 2024-12-20 16:27:10 Age [y:d:h:m:s]: 00:173:10:44:01
Block: 1179435 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123745 RingCT/type: yes/0
Extra: 018f2a45663f4880af59f26b8d823ffece5c2a44d1dade0fc99c39961f695fa1d80211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8f3da23134c8dc54a62ba3a872412985ef7e5cc675d2f76f468a7c8b8f2dd50 0.600000000000 1665830 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1179445, "vin": [ { "gen": { "height": 1179435 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8f3da23134c8dc54a62ba3a872412985ef7e5cc675d2f76f468a7c8b8f2dd50" } } ], "extra": [ 1, 143, 42, 69, 102, 63, 72, 128, 175, 89, 242, 107, 141, 130, 63, 254, 206, 92, 42, 68, 209, 218, 222, 15, 201, 156, 57, 150, 31, 105, 95, 161, 216, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8