Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 861c5d83392b58243d5064a36dfc75f5f3de928d30a04aa2713a45b737cd0e83

Tx prefix hash: 32841d8507c152ac298cf390854e555a07934807779c738be571c77a04521909
Tx public key: 3aa86f55c418ec6f1ce4e298f0b02f3ca1fbd388e5ecad1b3ba3b162d0ca34e4
Timestamp: 1716764440 Timestamp [UCT]: 2024-05-26 23:00:40 Age [y:d:h:m:s]: 00:157:10:33:28
Block: 1030739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112701 RingCT/type: yes/0
Extra: 013aa86f55c418ec6f1ce4e298f0b02f3ca1fbd388e5ecad1b3ba3b162d0ca34e4021100000001e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2db0213ae22366b80868f2f9b051bf375e0dd1139168d06b2d87866ae4b2314 0.600000000000 1499016 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": 1030749, "vin": [ { "gen": { "height": 1030739 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2db0213ae22366b80868f2f9b051bf375e0dd1139168d06b2d87866ae4b2314" } } ], "extra": [ 1, 58, 168, 111, 85, 196, 24, 236, 111, 28, 228, 226, 152, 240, 176, 47, 60, 161, 251, 211, 136, 229, 236, 173, 27, 59, 163, 177, 98, 208, 202, 52, 228, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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