Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fcdee53b1c1bbd2adcf2c4e402a8b91abcab78c009b65230f692fd66bbd5c5a1

Tx prefix hash: 7d77559e00f4501be3769e72522c713731873bf1723dbf6df73574c5466c207e
Tx public key: f1bb4fcb1be7ac574241554e8ef4bc2cb067b4274bbaddd3f69157caf2e58444
Timestamp: 1710877817 Timestamp [UCT]: 2024-03-19 19:50:17 Age [y:d:h:m:s]: 01:234:18:01:39
Block: 981947 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 426464 RingCT/type: yes/0
Extra: 01f1bb4fcb1be7ac574241554e8ef4bc2cb067b4274bbaddd3f69157caf2e584440211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79653e3dae15348c81910e7ab7fd4a11fdd221b217cef0f46f4247c1a12a65c0 0.600000000000 1442050 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": 981957, "vin": [ { "gen": { "height": 981947 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79653e3dae15348c81910e7ab7fd4a11fdd221b217cef0f46f4247c1a12a65c0" } } ], "extra": [ 1, 241, 187, 79, 203, 27, 231, 172, 87, 66, 65, 85, 78, 142, 244, 188, 44, 176, 103, 180, 39, 75, 186, 221, 211, 246, 145, 87, 202, 242, 229, 132, 68, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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