Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: feb4884876bdb9e81e8f00385cdfe484f5e9274e15961ef0e91242b35c3e9f3d

Tx prefix hash: 2babc3030c848b05444b4b248a17f1232e0926e2bd34310f9e1f827e3c0765a9
Tx public key: ecf7cca865726962a501f6a7c7d107c39e0142d8ef4b165bd5d294f8912e8410
Timestamp: 1703247844 Timestamp [UCT]: 2023-12-22 12:24:04 Age [y:d:h:m:s]: 01:331:09:44:04
Block: 918674 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 495700 RingCT/type: yes/0
Extra: 01ecf7cca865726962a501f6a7c7d107c39e0142d8ef4b165bd5d294f8912e841002110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1645947fe4b6f8dcbe149cee0077f8d69c8c8736daf65c52d4271062a896e83d 0.600000000000 1376326 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": 918684, "vin": [ { "gen": { "height": 918674 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1645947fe4b6f8dcbe149cee0077f8d69c8c8736daf65c52d4271062a896e83d" } } ], "extra": [ 1, 236, 247, 204, 168, 101, 114, 105, 98, 165, 1, 246, 167, 199, 209, 7, 195, 158, 1, 66, 216, 239, 75, 22, 91, 213, 210, 148, 248, 145, 46, 132, 16, 2, 17, 0, 0, 0, 4, 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