Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1965831c390be321984e12263295997291e4092cbdd5c3490d168857088b1d8

Tx prefix hash: 858a8499024a6ab3dc773f6fca643f7461f76f4ee55d390031e30a9460a8a248
Tx public key: a42924ea09d68a297d273862db5ed12851f9d8c1e2c2caea274aa33cd48c5924
Timestamp: 1763480561 Timestamp [UCT]: 2025-11-18 15:42:41 Age [y:d:h:m:s]: 00:009:14:14:32
Block: 1414900 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6875 RingCT/type: yes/0
Extra: 01a42924ea09d68a297d273862db5ed12851f9d8c1e2c2caea274aa33cd48c592402110000000334af31cc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b683e9eaa5aa4d9e1e9e46e8f10972e555d275dc8ac9e5381d2cb63532c55e76 0.600000000000 1903393 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": 1414910, "vin": [ { "gen": { "height": 1414900 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b683e9eaa5aa4d9e1e9e46e8f10972e555d275dc8ac9e5381d2cb63532c55e76" } } ], "extra": [ 1, 164, 41, 36, 234, 9, 214, 138, 41, 125, 39, 56, 98, 219, 94, 209, 40, 81, 249, 216, 193, 226, 194, 202, 234, 39, 74, 163, 60, 212, 140, 89, 36, 2, 17, 0, 0, 0, 3, 52, 175, 49, 204, 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