Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49d3042a24e6ca611b144da5d1ae541759d12108927a9c47b19cc0ef61d976c4

Tx prefix hash: 8122a6c5d4f8307a8b04c5f0c3f7c56877e9cb58c9639bd944bf6a0ab8c55ca9
Tx public key: bcfaa1edc25e2d9a21ae1f0e5f1d678e8384300e98901b122e02518ac47db58b
Timestamp: 1703695355 Timestamp [UCT]: 2023-12-27 16:42:35 Age [y:d:h:m:s]: 01:316:09:05:39
Block: 922380 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 484951 RingCT/type: yes/0
Extra: 01bcfaa1edc25e2d9a21ae1f0e5f1d678e8384300e98901b122e02518ac47db58b0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7306a81eb5b9593714be19eaa68e041a77fa7f5fa8f1a243aad130d40dab2a2 0.600000000000 1380076 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": 922390, "vin": [ { "gen": { "height": 922380 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7306a81eb5b9593714be19eaa68e041a77fa7f5fa8f1a243aad130d40dab2a2" } } ], "extra": [ 1, 188, 250, 161, 237, 194, 94, 45, 154, 33, 174, 31, 14, 95, 29, 103, 142, 131, 132, 48, 14, 152, 144, 27, 18, 46, 2, 81, 138, 196, 125, 181, 139, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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