Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 326156497aebff44ef791785caa084c71e7c7a07f7931619007087d96df85455

Tx prefix hash: 0bd8a1323970f59eb5326b1726b71aa1c2dcb7c33a355d28f75cbd9f5e9e93e9
Tx public key: 742e61b6cf075c1e35b0ecffdb40191a4f912f0b589d81c1462b14442942f6f2
Timestamp: 1583637703 Timestamp [UCT]: 2020-03-08 03:21:43 Age [y:d:h:m:s]: 05:248:15:11:35
Block: 78443 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1330816 RingCT/type: yes/0
Extra: 01742e61b6cf075c1e35b0ecffdb40191a4f912f0b589d81c1462b14442942f6f2021100000006e89b4e54000000000000000000

1 output(s) for total of 337.354548448000 dcy

stealth address amount amount idx
00: ebf48fdf6b5fd5699c910f2200cd54a8c9b1a6ede1664e1e6bf3f57111ccd801 337.354548448000 143897 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": 78453, "vin": [ { "gen": { "height": 78443 } } ], "vout": [ { "amount": 337354548448, "target": { "key": "ebf48fdf6b5fd5699c910f2200cd54a8c9b1a6ede1664e1e6bf3f57111ccd801" } } ], "extra": [ 1, 116, 46, 97, 182, 207, 7, 92, 30, 53, 176, 236, 255, 219, 64, 25, 26, 79, 145, 47, 11, 88, 157, 129, 193, 70, 43, 20, 68, 41, 66, 246, 242, 2, 17, 0, 0, 0, 6, 232, 155, 78, 84, 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