Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e95c1e29f8cc15bb730c7038aecbd8a3820540bc7d29235b8ef3d8607a59568

Tx prefix hash: 72344464bf270204b169cbb74bcaf191b7476e508b2d6693a292666f00c3e918
Tx public key: 0cbf73cac40bb47bf77e1ae2ed6040ca79ca1a611bc9250eb54c5205d0b9bd3c
Timestamp: 1724364642 Timestamp [UCT]: 2024-08-22 22:10:42 Age [y:d:h:m:s]: 00:250:04:00:27
Block: 1093753 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178668 RingCT/type: yes/0
Extra: 010cbf73cac40bb47bf77e1ae2ed6040ca79ca1a611bc9250eb54c5205d0b9bd3c021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2df64c41b09ba17e4a7d7bfa44c0d4ff8fdca39750f911d51130005fc748a0e7 0.600000000000 1568760 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": 1093763, "vin": [ { "gen": { "height": 1093753 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2df64c41b09ba17e4a7d7bfa44c0d4ff8fdca39750f911d51130005fc748a0e7" } } ], "extra": [ 1, 12, 191, 115, 202, 196, 11, 180, 123, 247, 126, 26, 226, 237, 96, 64, 202, 121, 202, 26, 97, 27, 201, 37, 14, 181, 76, 82, 5, 208, 185, 189, 60, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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