Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f914f6f80668af102eed76035a27eb80bf355986aa587bde5b3b5123bb8c4d1d

Tx prefix hash: 954cc089e509b80a362c05cb3a403b6e25e467cd8461e7cb22e227653739ed17
Tx public key: 3fbe4d920b643d191c305ef88b640d2b13c857f9c3fec34cf8f972922117357a
Timestamp: 1722371381 Timestamp [UCT]: 2024-07-30 20:29:41 Age [y:d:h:m:s]: 00:231:21:40:07
Block: 1077207 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165660 RingCT/type: yes/0
Extra: 013fbe4d920b643d191c305ef88b640d2b13c857f9c3fec34cf8f972922117357a021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4792ccc6d927f68bbafa822d83458eec6d8e9f441cfd36f26f2b60ae58cecc4 0.600000000000 1549754 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": 1077217, "vin": [ { "gen": { "height": 1077207 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4792ccc6d927f68bbafa822d83458eec6d8e9f441cfd36f26f2b60ae58cecc4" } } ], "extra": [ 1, 63, 190, 77, 146, 11, 100, 61, 25, 28, 48, 94, 248, 139, 100, 13, 43, 19, 200, 87, 249, 195, 254, 195, 76, 248, 249, 114, 146, 33, 23, 53, 122, 2, 17, 0, 0, 0, 7, 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