Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14b6b5aff7febbea8839ed6d1353612f1b17fef3365c354221b969b3473c8d83

Tx prefix hash: 95eabbcc82b33595989d2688ca59b06fb7d673bcbdca9179e531a893e1c413e2
Tx public key: d089b028fc5f851209dd2b8681b572786e3e67c54b2c8f544123192b6f7d1c99
Timestamp: 1704282919 Timestamp [UCT]: 2024-01-03 11:55:19 Age [y:d:h:m:s]: 01:306:03:06:58
Block: 927253 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 477606 RingCT/type: yes/0
Extra: 01d089b028fc5f851209dd2b8681b572786e3e67c54b2c8f544123192b6f7d1c9902110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3b968a4f96135de7e2cd14136a541544bf8bc8e375a658b655ee4673253a88c 0.600000000000 1385065 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": 927263, "vin": [ { "gen": { "height": 927253 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3b968a4f96135de7e2cd14136a541544bf8bc8e375a658b655ee4673253a88c" } } ], "extra": [ 1, 208, 137, 176, 40, 252, 95, 133, 18, 9, 221, 43, 134, 129, 181, 114, 120, 110, 62, 103, 197, 75, 44, 143, 84, 65, 35, 25, 43, 111, 125, 28, 153, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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