Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 349a973b2673659e5fffcdf87253f0947daf882b81b41b6e7e67b614722fd270

Tx prefix hash: 1b11c1917cc9aee5629e0453f55b253630d12c5aa801e510dda68e5cd8e4aff0
Tx public key: 163894e51d91fa89b6d193ffdab891d4a0f67015c5859554f089da263dc94d81
Timestamp: 1764599701 Timestamp [UCT]: 2025-12-01 14:35:01 Age [y:d:h:m:s]: 00:020:22:13:14
Block: 1424175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14984 RingCT/type: yes/0
Extra: 01163894e51d91fa89b6d193ffdab891d4a0f67015c5859554f089da263dc94d81021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 021d96066dcc922c4c63b382a050efb2816a0fab6683be509930b05c7aa10a69 0.600000000000 1912804 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": 1424185, "vin": [ { "gen": { "height": 1424175 } } ], "vout": [ { "amount": 600000000, "target": { "key": "021d96066dcc922c4c63b382a050efb2816a0fab6683be509930b05c7aa10a69" } } ], "extra": [ 1, 22, 56, 148, 229, 29, 145, 250, 137, 182, 209, 147, 255, 218, 184, 145, 212, 160, 246, 112, 21, 197, 133, 149, 84, 240, 137, 218, 38, 61, 201, 77, 129, 2, 17, 0, 0, 0, 1, 214, 225, 157, 124, 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