Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fdfeea8644cd8aab4241f652debbb30bc353c51e25b5275acfb87b0d4bc40fef

Tx prefix hash: db0c837acc6194f20e96e30c7069d77e007769be495983fe33e059ef2af1b0fb
Tx public key: 4bc8b51728332564fb4add93f826f57cbc39c28246e32d71b98da929c83b0af1
Timestamp: 1709300891 Timestamp [UCT]: 2024-03-01 13:48:11 Age [y:d:h:m:s]: 01:244:23:00:14
Block: 968865 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 433805 RingCT/type: yes/0
Extra: 014bc8b51728332564fb4add93f826f57cbc39c28246e32d71b98da929c83b0af102110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7f708fc39b122b9b3372a0d7fb74f247b036721c60736e8509a1441271b0d4d 0.600000000000 1428688 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": 968875, "vin": [ { "gen": { "height": 968865 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7f708fc39b122b9b3372a0d7fb74f247b036721c60736e8509a1441271b0d4d" } } ], "extra": [ 1, 75, 200, 181, 23, 40, 51, 37, 100, 251, 74, 221, 147, 248, 38, 245, 124, 188, 57, 194, 130, 70, 227, 45, 113, 185, 141, 169, 41, 200, 59, 10, 241, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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