Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f6ea29d94269aba9913a076f072a6b560857146b632ef6d64db26ab51810acb

Tx prefix hash: f23dfdadb2822f6d6e55b5ed49bdd8b07736be4af24f22fdb668dcd0293e308c
Tx public key: 8ec86ea20e1a5ee358edd8755b44f0056a0c3a97175ee26b725009a6d96a085c
Timestamp: 1720220761 Timestamp [UCT]: 2024-07-05 23:06:01 Age [y:d:h:m:s]: 00:292:21:00:43
Block: 1059380 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209277 RingCT/type: yes/0
Extra: 018ec86ea20e1a5ee358edd8755b44f0056a0c3a97175ee26b725009a6d96a085c02110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c22f4ba4acb6af0f8b73fbc54b9d2c6c3ba65884d40e61a585bc189ce466ddf0 0.600000000000 1529847 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": 1059390, "vin": [ { "gen": { "height": 1059380 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c22f4ba4acb6af0f8b73fbc54b9d2c6c3ba65884d40e61a585bc189ce466ddf0" } } ], "extra": [ 1, 142, 200, 110, 162, 14, 26, 94, 227, 88, 237, 216, 117, 91, 68, 240, 5, 106, 12, 58, 151, 23, 94, 226, 107, 114, 80, 9, 166, 217, 106, 8, 92, 2, 17, 0, 0, 0, 8, 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