Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 582e3b854ffe4b78b00e9a85d96eb3b627f74634d67c033230aefcf3fdb1d45a

Tx prefix hash: c84b8f8d671eb94a95c7e051f2967ff15d87d3d48f9fb6992631babcb60ab24d
Tx public key: 70577ccbd32808d8e213e59133b64d1dc61c22aa1991ec6480b0b5a1793b1730
Timestamp: 1724453279 Timestamp [UCT]: 2024-08-23 22:47:59 Age [y:d:h:m:s]: 00:216:13:30:40
Block: 1094485 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154628 RingCT/type: yes/0
Extra: 0170577ccbd32808d8e213e59133b64d1dc61c22aa1991ec6480b0b5a1793b1730021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e409d32f99b66b7fe8fafdca3f43fcdffefe07c3ac19413512694025cbbb2fff 0.600000000000 1569602 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": 1094495, "vin": [ { "gen": { "height": 1094485 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e409d32f99b66b7fe8fafdca3f43fcdffefe07c3ac19413512694025cbbb2fff" } } ], "extra": [ 1, 112, 87, 124, 203, 211, 40, 8, 216, 226, 19, 229, 145, 51, 182, 77, 29, 198, 28, 34, 170, 25, 145, 236, 100, 128, 176, 181, 161, 121, 59, 23, 48, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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