Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b047d885e00c2794ac78568174b6ba6607137263923b6b34030aa91c392fe10f

Tx prefix hash: 437e6aeeb89d564b4f2a0e35cfcf4f0132766cbd51c11732b718f44adb4e1338
Tx public key: 542eeb7a72d8c8196d131ea19c2e8a937c7bf5e4457f4ccb81a4f1948f29aa35
Timestamp: 1753030877 Timestamp [UCT]: 2025-07-20 17:01:17 Age [y:d:h:m:s]: 00:123:22:02:09
Block: 1329659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87361 RingCT/type: yes/0
Extra: 01542eeb7a72d8c8196d131ea19c2e8a937c7bf5e4457f4ccb81a4f1948f29aa35021100000004bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8271b47e276271c02500fe99e6ae16c0142343a0239437c9769fdb136ab5bef4 0.600000000000 1817448 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": 1329669, "vin": [ { "gen": { "height": 1329659 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8271b47e276271c02500fe99e6ae16c0142343a0239437c9769fdb136ab5bef4" } } ], "extra": [ 1, 84, 46, 235, 122, 114, 216, 200, 25, 109, 19, 30, 161, 156, 46, 138, 147, 124, 123, 245, 228, 69, 127, 76, 203, 129, 164, 241, 148, 143, 41, 170, 53, 2, 17, 0, 0, 0, 4, 191, 81, 178, 162, 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