Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2bfc4499dedf8a5309a2b1d6a055255a4859bf4a2b89db721a14b06eede5eb4

Tx prefix hash: 980821211cdf2785149215816b1706a8610715789871f8b3c156bd873731cd6d
Tx public key: d194efdf157ab82f478f0daf40d1c6a9a21a8860b8bb897d8cf9a747f453aff1
Timestamp: 1711681637 Timestamp [UCT]: 2024-03-29 03:07:17 Age [y:d:h:m:s]: 01:047:03:30:40
Block: 988608 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294679 RingCT/type: yes/0
Extra: 01d194efdf157ab82f478f0daf40d1c6a9a21a8860b8bb897d8cf9a747f453aff102110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c60d8937c05df602b5fe799d01697ce8d5cb2c78d060f2a3a8c87db0f4ed83d4 0.600000000000 1448889 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": 988618, "vin": [ { "gen": { "height": 988608 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c60d8937c05df602b5fe799d01697ce8d5cb2c78d060f2a3a8c87db0f4ed83d4" } } ], "extra": [ 1, 209, 148, 239, 223, 21, 122, 184, 47, 71, 143, 13, 175, 64, 209, 198, 169, 162, 26, 136, 96, 184, 187, 137, 125, 140, 249, 167, 71, 244, 83, 175, 241, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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