Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79f4694f9f7775cedc07faaa9c141fa0efbf3b6e432cb901bbb5964f7a0fee33

Tx prefix hash: c49680be37c41b33babe8dae2f41c241a44ab18d2466ff59e3969bc3b5a50861
Tx public key: 077a7ea0b6fb7e63854e2f530090b06699ab0d146341910c636614888abcd954
Timestamp: 1702583555 Timestamp [UCT]: 2023-12-14 19:52:35 Age [y:d:h:m:s]: 01:152:16:04:35
Block: 913154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370285 RingCT/type: yes/0
Extra: 01077a7ea0b6fb7e63854e2f530090b06699ab0d146341910c636614888abcd95402110000000575e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3e642850dcb87c6d7e17acc06014e27421d468db03b72777f4b8669e7cefef5 0.600000000000 1370400 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": 913164, "vin": [ { "gen": { "height": 913154 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3e642850dcb87c6d7e17acc06014e27421d468db03b72777f4b8669e7cefef5" } } ], "extra": [ 1, 7, 122, 126, 160, 182, 251, 126, 99, 133, 78, 47, 83, 0, 144, 176, 102, 153, 171, 13, 20, 99, 65, 145, 12, 99, 102, 20, 136, 138, 188, 217, 84, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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