Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84ad0aa486e8e25fe674fa298b23ab828c13d8eb9441d406dd6918ce850d92db

Tx prefix hash: e621f70f6bcdf3ca7d3a3e300ec0cee6532309e980e0e90d8876bbf4061e92b0
Tx public key: e540a509afb95363353f5a3da342411757a5e6c2f798bbc70e4edbe68a7e5276
Timestamp: 1723352455 Timestamp [UCT]: 2024-08-11 05:00:55 Age [y:d:h:m:s]: 00:308:17:17:50
Block: 1085349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220476 RingCT/type: yes/0
Extra: 01e540a509afb95363353f5a3da342411757a5e6c2f798bbc70e4edbe68a7e527602110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e86bfc791c954ae5d884817f20d9b3a63ffec11df19c44aa73503bac997aa09 0.600000000000 1559914 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": 1085359, "vin": [ { "gen": { "height": 1085349 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e86bfc791c954ae5d884817f20d9b3a63ffec11df19c44aa73503bac997aa09" } } ], "extra": [ 1, 229, 64, 165, 9, 175, 185, 83, 99, 53, 63, 90, 61, 163, 66, 65, 23, 87, 165, 230, 194, 247, 152, 187, 199, 14, 78, 219, 230, 138, 126, 82, 118, 2, 17, 0, 0, 0, 8, 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