Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18dce57fcd918252d094c2aa7434f34686a048f51ce983b9415006a887a7be26

Tx prefix hash: abb54bd4a5210707a1ad0c09e6d575ef7df53762de4b1d4327a6e1ff75dfd844
Tx public key: bed05de8923891478e0a8ec303c94a6a20616b1158565d620fbec3c659365b7c
Timestamp: 1731865035 Timestamp [UCT]: 2024-11-17 17:37:15 Age [y:d:h:m:s]: 00:186:10:52:54
Block: 1155834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133112 RingCT/type: yes/0
Extra: 01bed05de8923891478e0a8ec303c94a6a20616b1158565d620fbec3c659365b7c0211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ed858f8bb42d5e397555e312a2b7b9e4d9f5f8a8f2a913b495cdf2f30222f2c4 0.600000000000 1641453 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": 1155844, "vin": [ { "gen": { "height": 1155834 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed858f8bb42d5e397555e312a2b7b9e4d9f5f8a8f2a913b495cdf2f30222f2c4" } } ], "extra": [ 1, 190, 208, 93, 232, 146, 56, 145, 71, 142, 10, 142, 195, 3, 201, 74, 106, 32, 97, 107, 17, 88, 86, 93, 98, 15, 190, 195, 198, 89, 54, 91, 124, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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