Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a42897b117347ab5e2d013ef931619b62edcfacd9842d0b45c746459b6262c6

Tx prefix hash: e0b0a83c98a7c0dd174f661a87504bd2b877a0fbddf001d42d0e37fb076fd899
Tx public key: 0ab2d9b013bc70b07ba2a6b12989c8a7e3b89df272d57a992506d174637528fd
Timestamp: 1577898937 Timestamp [UCT]: 2020-01-01 17:15:37 Age [y:d:h:m:s]: 05:001:20:19:58
Block: 36466 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1151443 RingCT/type: yes/0
Extra: 010ab2d9b013bc70b07ba2a6b12989c8a7e3b89df272d57a992506d174637528fd021100000029d81c26c0000000000000000000

1 output(s) for total of 464.701267511000 dcy

stealth address amount amount idx
00: 11597ea1cc1d2bc5e832a409db18dd6de0901feebe3884fcba8f7db65447ba6b 464.701267511000 61789 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": 36476, "vin": [ { "gen": { "height": 36466 } } ], "vout": [ { "amount": 464701267511, "target": { "key": "11597ea1cc1d2bc5e832a409db18dd6de0901feebe3884fcba8f7db65447ba6b" } } ], "extra": [ 1, 10, 178, 217, 176, 19, 188, 112, 176, 123, 162, 166, 177, 41, 137, 200, 167, 227, 184, 157, 242, 114, 213, 122, 153, 37, 6, 209, 116, 99, 117, 40, 253, 2, 17, 0, 0, 0, 41, 216, 28, 38, 192, 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