Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77a5193e2ba1352a177495ec2170a11868b98e72f196a75a034f83fb2ea69d96

Tx prefix hash: 19f59fe7c25a21be79e94f7e6cbe57659a74105420ea7152a7961414ab9bc666
Tx public key: 1d6a2e10977c019b2e9be762466c8a0ec1ce33032bd748014eb91ad7c7ec650d
Timestamp: 1738884835 Timestamp [UCT]: 2025-02-06 23:33:55 Age [y:d:h:m:s]: 00:287:15:30:48
Block: 1213691 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203329 RingCT/type: yes/0
Extra: 011d6a2e10977c019b2e9be762466c8a0ec1ce33032bd748014eb91ad7c7ec650d021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bfd4338e8aa3cfbcf0d047c1bb4400b6a662318f3df9f9bdad8f5b282c2bf67b 0.600000000000 1700472 of 15

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": 1213701, "vin": [ { "gen": { "height": 1213691 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfd4338e8aa3cfbcf0d047c1bb4400b6a662318f3df9f9bdad8f5b282c2bf67b" } } ], "extra": [ 1, 29, 106, 46, 16, 151, 124, 1, 155, 46, 155, 231, 98, 70, 108, 138, 14, 193, 206, 51, 3, 43, 215, 72, 1, 78, 185, 26, 215, 199, 236, 101, 13, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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