Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 775b1beab39f45aebfc717e3d530aa72ec66a5429308074c52796f7ac4709a27

Tx prefix hash: 1ea50fcf309d7ccdbe4263834d2ba1858390c62ff46e139ecb41ff61bb7ca0cd
Tx public key: 3d40ebd617dc188ce31f716001ea58817f31393766d6d3932a0e131f9c198db2
Timestamp: 1755462722 Timestamp [UCT]: 2025-08-17 20:32:02 Age [y:d:h:m:s]: 00:049:03:58:07
Block: 1348729 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34923 RingCT/type: yes/0
Extra: 013d40ebd617dc188ce31f716001ea58817f31393766d6d3932a0e131f9c198db2021100000009ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b42a174315a7f2df50f2b17f5861d2832fc6659e7dcc61b4303e9fd96e5d6637 0.600000000000 1836658 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": 1348739, "vin": [ { "gen": { "height": 1348729 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b42a174315a7f2df50f2b17f5861d2832fc6659e7dcc61b4303e9fd96e5d6637" } } ], "extra": [ 1, 61, 64, 235, 214, 23, 220, 24, 140, 227, 31, 113, 96, 1, 234, 88, 129, 127, 49, 57, 55, 102, 214, 211, 147, 42, 14, 19, 31, 156, 25, 141, 178, 2, 17, 0, 0, 0, 9, 173, 121, 72, 208, 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