Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ae6f6f26852afffc0fea2fa9c7ec1af97e4f7da3f826ba35f7b4214ddf82883

Tx prefix hash: 3bd3928253ffd251d979432151334e234188354a0eeabe46dbb7b0442491d571
Tx public key: 7bcc01eb9b06d4e8875caf5b55458a88b31bbc33dc38db5399d1dddcc6a1f0ce
Timestamp: 1578186777 Timestamp [UCT]: 2020-01-05 01:12:57 Age [y:d:h:m:s]: 04:301:22:37:25
Block: 38891 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1104957 RingCT/type: yes/0
Extra: 017bcc01eb9b06d4e8875caf5b55458a88b31bbc33dc38db5399d1dddcc6a1f0ce0211000000104943cd9f000000000000000000

1 output(s) for total of 456.182711037000 dcy

stealth address amount amount idx
00: 393344703e5cc978e6ea7743959ecfd77f90006442119eb5274bb0cb605af080 456.182711037000 66656 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": 38901, "vin": [ { "gen": { "height": 38891 } } ], "vout": [ { "amount": 456182711037, "target": { "key": "393344703e5cc978e6ea7743959ecfd77f90006442119eb5274bb0cb605af080" } } ], "extra": [ 1, 123, 204, 1, 235, 155, 6, 212, 232, 135, 92, 175, 91, 85, 69, 138, 136, 179, 27, 188, 51, 220, 56, 219, 83, 153, 209, 221, 220, 198, 161, 240, 206, 2, 17, 0, 0, 0, 16, 73, 67, 205, 159, 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