Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82752f9e4509c9488e9256e57914622580e99154d4f6fa193dc24b80ee5af706

Tx prefix hash: 9a8a78a5af5951e9e1b6f96c4e928edf29c154a0626d11a6e499e26e36eb680d
Tx public key: 0acf067be585f11edbe2abcaa2daa1ca17a5b5760bf82e281baee2bfb0ba9b78
Timestamp: 1579990652 Timestamp [UCT]: 2020-01-25 22:17:32 Age [y:d:h:m:s]: 04:339:13:10:15
Block: 52752 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1132938 RingCT/type: yes/0
Extra: 010acf067be585f11edbe2abcaa2daa1ca17a5b5760bf82e281baee2bfb0ba9b7802110000000b4ac5aa02000000000000000000

1 output(s) for total of 410.403971254000 dcy

stealth address amount amount idx
00: 3db22e4ec7e0e94fd3e0a37d21a913b67b740bd931ee5a86cf80cc9526ce2a2a 410.403971254000 97877 of 0

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": 52762, "vin": [ { "gen": { "height": 52752 } } ], "vout": [ { "amount": 410403971254, "target": { "key": "3db22e4ec7e0e94fd3e0a37d21a913b67b740bd931ee5a86cf80cc9526ce2a2a" } } ], "extra": [ 1, 10, 207, 6, 123, 229, 133, 241, 30, 219, 226, 171, 202, 162, 218, 161, 202, 23, 165, 181, 118, 11, 248, 46, 40, 27, 174, 226, 191, 176, 186, 155, 120, 2, 17, 0, 0, 0, 11, 74, 197, 170, 2, 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