Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c51a0982f4b360490c624a2293c79e71e3f67b31ee7ba7d8fd39be6588688e0

Tx prefix hash: 9e2147c5c649d5242a283398a3eb4d3f39e9ef27228791eda35eef3fe5a99bb1
Tx public key: 990db553b8115aee16c0cb9a20927e8198d05ba804c451c94af14895a0cdfab1
Timestamp: 1714339967 Timestamp [UCT]: 2024-04-28 21:32:47 Age [y:d:h:m:s]: 00:256:01:00:28
Block: 1010625 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183274 RingCT/type: yes/0
Extra: 01990db553b8115aee16c0cb9a20927e8198d05ba804c451c94af14895a0cdfab102110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c9f21d6fe016e15fea8a33fee096b1d318f68b40d8fa25d6d8bc155b11196318 0.600000000000 1472635 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": 1010635, "vin": [ { "gen": { "height": 1010625 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c9f21d6fe016e15fea8a33fee096b1d318f68b40d8fa25d6d8bc155b11196318" } } ], "extra": [ 1, 153, 13, 181, 83, 184, 17, 90, 238, 22, 192, 203, 154, 32, 146, 126, 129, 152, 208, 91, 168, 4, 196, 81, 201, 74, 241, 72, 149, 160, 205, 250, 177, 2, 17, 0, 0, 0, 4, 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