Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9f96b9ba5317384be4a694a72ef91ba4b06e3f7727d2d55e56d36a3f3f93a93

Tx prefix hash: fe62b8b9df05e2fa2bf9b70ab48f8871cf2c0f7ab5f02ea074b5adccde18ad08
Tx public key: 0d614009879e16f0ab811937405ad81e931ce40ec05a8591f4007b872b2a309a
Timestamp: 1577862691 Timestamp [UCT]: 2020-01-01 07:11:31 Age [y:d:h:m:s]: 04:310:20:21:28
Block: 36196 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1111337 RingCT/type: yes/0
Extra: 010d614009879e16f0ab811937405ad81e931ce40ec05a8591f4007b872b2a309a0211000000084ac5aa02000000000000000000

1 output(s) for total of 465.659512904000 dcy

stealth address amount amount idx
00: f943a8b61f0808171ee4c45e90c94dfb5e1ee76a06af19e44fc7ea251695e6df 465.659512904000 61240 of 0

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": 36206, "vin": [ { "gen": { "height": 36196 } } ], "vout": [ { "amount": 465659512904, "target": { "key": "f943a8b61f0808171ee4c45e90c94dfb5e1ee76a06af19e44fc7ea251695e6df" } } ], "extra": [ 1, 13, 97, 64, 9, 135, 158, 22, 240, 171, 129, 25, 55, 64, 90, 216, 30, 147, 28, 228, 14, 192, 90, 133, 145, 244, 0, 123, 135, 43, 42, 48, 154, 2, 17, 0, 0, 0, 8, 74, 197, 170, 2, 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