Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 698399f6acb22cb1b1b4ac88d07dbd7b2c960b73d9ee4adb8b136395f4971bd9

Tx prefix hash: 2002c607ea4eb2d6b7c3ca222a686b856913596199fa5e105a52e3b44dfdd605
Tx public key: 0ab82e047157c811b0016e58b1cd61ababc52aa60f20e908765b44a510af01e3
Timestamp: 1721318221 Timestamp [UCT]: 2024-07-18 15:57:01 Age [y:d:h:m:s]: 01:082:23:25:58
Block: 1068503 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317744 RingCT/type: yes/0
Extra: 010ab82e047157c811b0016e58b1cd61ababc52aa60f20e908765b44a510af01e302110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4cc81f2ed37af2a72d25259002fcdd1a7e9888a8aa1332a5cfccee874df0462e 0.600000000000 1539582 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": 1068513, "vin": [ { "gen": { "height": 1068503 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4cc81f2ed37af2a72d25259002fcdd1a7e9888a8aa1332a5cfccee874df0462e" } } ], "extra": [ 1, 10, 184, 46, 4, 113, 87, 200, 17, 176, 1, 110, 88, 177, 205, 97, 171, 171, 197, 42, 166, 15, 32, 233, 8, 118, 91, 68, 165, 16, 175, 1, 227, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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