Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 675e746f259ceb7eca0a65ea2257c4e5bae4dbebc2d0bfbc608793c72c98398e

Tx prefix hash: 67ecc43cfab3ef2f8cbbf720219d5a329d74e15ae888b94c99595f1bd315782d
Tx public key: 5f2e57a1f8fb83ba09fc0c46e1f8245ce3ca76f85a59ec99b13dcf18b05962c9
Timestamp: 1587855155 Timestamp [UCT]: 2020-04-25 22:52:35 Age [y:d:h:m:s]: 04:247:23:30:23
Block: 96223 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1089081 RingCT/type: yes/0
Extra: 015f2e57a1f8fb83ba09fc0c46e1f8245ce3ca76f85a59ec99b13dcf18b05962c902110000007ca86a1a65000000000000000000

1 output(s) for total of 294.560171742000 dcy

stealth address amount amount idx
00: cd72e4f76f5430c8c3bed32e8b13c5b6b494e58ffbfbfd234fe54d17ab5fc171 294.560171742000 170750 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": 96233, "vin": [ { "gen": { "height": 96223 } } ], "vout": [ { "amount": 294560171742, "target": { "key": "cd72e4f76f5430c8c3bed32e8b13c5b6b494e58ffbfbfd234fe54d17ab5fc171" } } ], "extra": [ 1, 95, 46, 87, 161, 248, 251, 131, 186, 9, 252, 12, 70, 225, 248, 36, 92, 227, 202, 118, 248, 90, 89, 236, 153, 177, 61, 207, 24, 176, 89, 98, 201, 2, 17, 0, 0, 0, 124, 168, 106, 26, 101, 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