Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 279b102826a216d7a63eae54ec5534c5cc4a93e721b627fe95a79f3afc42a8fd

Tx prefix hash: 95d1d958e7a2d6e884b9b8b6d82d1dbe1b0a7530dc502768db66097d11385113
Tx public key: e51eb4c822b3f1c802d5173af11276dab9133235813ee90d79cc3b9290b8cbca
Timestamp: 1732194551 Timestamp [UCT]: 2024-11-21 13:09:11 Age [y:d:h:m:s]: 00:002:12:39:49
Block: 1158553 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1822 RingCT/type: yes/0
Extra: 01e51eb4c822b3f1c802d5173af11276dab9133235813ee90d79cc3b9290b8cbca0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e11f93d203965d5396466b3ecdcae7c3d2b6585a40dbcedcf4f50637d113ee0 0.600000000000 1644182 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": 1158563, "vin": [ { "gen": { "height": 1158553 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e11f93d203965d5396466b3ecdcae7c3d2b6585a40dbcedcf4f50637d113ee0" } } ], "extra": [ 1, 229, 30, 180, 200, 34, 179, 241, 200, 2, 213, 23, 58, 241, 18, 118, 218, 185, 19, 50, 53, 129, 62, 233, 13, 121, 204, 59, 146, 144, 184, 203, 202, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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