Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe262c610681663d41f4c28dc35617d8b2e96dc1a21f845c73f9fe10ea00d151

Tx prefix hash: eef695b310cbb06d9461708f06796ce3b37807711f710220d04dedf7f5bf287d
Tx public key: 0e519b24eeba16d01216ca48610a679fced2b4e09a743dfc88e71e589018c8ef
Timestamp: 1648690315 Timestamp [UCT]: 2022-03-31 01:31:55 Age [y:d:h:m:s]: 02:313:14:15:20
Block: 469960 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 743504 RingCT/type: yes/0
Extra: 010e519b24eeba16d01216ca48610a679fced2b4e09a743dfc88e71e589018c8ef02110000000e5eb576c5000000000000000000

1 output(s) for total of 17.016722568000 dcy

stealth address amount amount idx
00: 7a2b0c79795475cf1fabce99f111d7f64ffc46ed8586477ea14a34eca6af0f35 17.016722568000 889010 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": 469970, "vin": [ { "gen": { "height": 469960 } } ], "vout": [ { "amount": 17016722568, "target": { "key": "7a2b0c79795475cf1fabce99f111d7f64ffc46ed8586477ea14a34eca6af0f35" } } ], "extra": [ 1, 14, 81, 155, 36, 238, 186, 22, 208, 18, 22, 202, 72, 97, 10, 103, 159, 206, 210, 180, 224, 154, 116, 61, 252, 136, 231, 30, 88, 144, 24, 200, 239, 2, 17, 0, 0, 0, 14, 94, 181, 118, 197, 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