Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af094b189a8992b2e6257468d7f0d2985797b341f2f7d258bc32c0d70a026b78

Tx prefix hash: ddccc51843c375aba1af0254dc9ae1951649f25ad4274f2fd56a4772de7aaeb6
Tx public key: bc32f4e526e6eeb654d4db9ec4456cdcfbed5066577a0bdc8185d72a82a26333
Timestamp: 1705803980 Timestamp [UCT]: 2024-01-21 02:26:20 Age [y:d:h:m:s]: 01:147:00:24:06
Block: 939830 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366137 RingCT/type: yes/0
Extra: 01bc32f4e526e6eeb654d4db9ec4456cdcfbed5066577a0bdc8185d72a82a2633302110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c37e9fb3667ec9dde5a8e06feff63241854ff4381657f2e84863ae04186e2d0 0.600000000000 1397962 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": 939840, "vin": [ { "gen": { "height": 939830 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c37e9fb3667ec9dde5a8e06feff63241854ff4381657f2e84863ae04186e2d0" } } ], "extra": [ 1, 188, 50, 244, 229, 38, 230, 238, 182, 84, 212, 219, 158, 196, 69, 108, 220, 251, 237, 80, 102, 87, 122, 11, 220, 129, 133, 215, 42, 130, 162, 99, 51, 2, 17, 0, 0, 0, 2, 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