Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2980816b935edcb7a684f69ab64e5a6380e300b6860ed1617bae31d341be7cf4

Tx prefix hash: a4f9fd5ed0f457deb6fb3bea0b1c147fd9537da26707c12d5b6aebeebadcab6a
Tx public key: 1b7236242232082736544b18e39a744e9f0cde6457a916768511e8fc1f3ebcd3
Timestamp: 1731717923 Timestamp [UCT]: 2024-11-16 00:45:23 Age [y:d:h:m:s]: 00:166:16:01:09
Block: 1154619 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118945 RingCT/type: yes/0
Extra: 011b7236242232082736544b18e39a744e9f0cde6457a916768511e8fc1f3ebcd30211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b24103291e1547aef3e6a483acd76d654332565f05ff3cf5cf31b1f3580df1d2 0.600000000000 1640232 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": 1154629, "vin": [ { "gen": { "height": 1154619 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b24103291e1547aef3e6a483acd76d654332565f05ff3cf5cf31b1f3580df1d2" } } ], "extra": [ 1, 27, 114, 54, 36, 34, 50, 8, 39, 54, 84, 75, 24, 227, 154, 116, 78, 159, 12, 222, 100, 87, 169, 22, 118, 133, 17, 232, 252, 31, 62, 188, 211, 2, 17, 0, 0, 0, 5, 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