Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed2cfb4cecc913a95b0c97b24d1aaa7902542e9dac21fc08e6f6599f881e47c8

Tx prefix hash: 204f207dbd2e70bab226f43e3afb712776d69d51e90ffc710d7e9e5469b63247
Tx public key: 204d61dfa0b5b5c677c166c560410f75efc5f7fbaf92f0b3ac74d0c8c188ac87
Timestamp: 1700409290 Timestamp [UCT]: 2023-11-19 15:54:50 Age [y:d:h:m:s]: 01:178:02:47:05
Block: 895131 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388502 RingCT/type: yes/0
Extra: 01204d61dfa0b5b5c677c166c560410f75efc5f7fbaf92f0b3ac74d0c8c188ac87021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.663833861000 dcy

stealth address amount amount idx
00: f0a2d7e298dc0f104755f040d20c746f5e4d2635fbcddb92a068bfdaee1b5b15 0.663833861000 1351354 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": 895141, "vin": [ { "gen": { "height": 895131 } } ], "vout": [ { "amount": 663833861, "target": { "key": "f0a2d7e298dc0f104755f040d20c746f5e4d2635fbcddb92a068bfdaee1b5b15" } } ], "extra": [ 1, 32, 77, 97, 223, 160, 181, 181, 198, 119, 193, 102, 197, 96, 65, 15, 117, 239, 197, 247, 251, 175, 146, 240, 179, 172, 116, 208, 200, 193, 136, 172, 135, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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