Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56095e375be8d23fe5f00e1bb0f64ef6a7d924c3cd59e291c46b4d3e4c38552c

Tx prefix hash: 74ff76c986c8f602b793fea619116684fb297cc101080573b1beb77ff5ed870a
Tx public key: dafd026d46cc7f209dd336fd49eebab9a5707a8afa57800601a97a983e2c930c
Timestamp: 1677215662 Timestamp [UCT]: 2023-02-24 05:14:22 Age [y:d:h:m:s]: 02:049:05:33:06
Block: 703740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 556775 RingCT/type: yes/0
Extra: 01dafd026d46cc7f209dd336fd49eebab9a5707a8afa57800601a97a983e2c930c02110000000674b6d784000000000000000000

1 output(s) for total of 2.859019723000 dcy

stealth address amount amount idx
00: c006de5eefde28d5667bbd69f85c3a2707ed71ea71d08d9010ca7060c4e022bc 2.859019723000 1147343 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": 703750, "vin": [ { "gen": { "height": 703740 } } ], "vout": [ { "amount": 2859019723, "target": { "key": "c006de5eefde28d5667bbd69f85c3a2707ed71ea71d08d9010ca7060c4e022bc" } } ], "extra": [ 1, 218, 253, 2, 109, 70, 204, 127, 32, 157, 211, 54, 253, 73, 238, 186, 185, 165, 112, 122, 138, 250, 87, 128, 6, 1, 169, 122, 152, 62, 44, 147, 12, 2, 17, 0, 0, 0, 6, 116, 182, 215, 132, 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