Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b1973914cb9ab0069b2ff55b165f5b4fa323cc7f350a9b7690548ff1bc3f879

Tx prefix hash: 7a4028fe9f1197cb0735aa3c1d60a56e1f15c1f1fe838030c1c8e8cd801de15b
Tx public key: 6d3fa23dbac8073d2100b6573e4c87ad4338e4885f5340e9ebf9f28b4f090609
Timestamp: 1756322763 Timestamp [UCT]: 2025-08-27 19:26:03 Age [y:d:h:m:s]: 00:156:09:50:42
Block: 1355773 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111618 RingCT/type: yes/0
Extra: 016d3fa23dbac8073d2100b6573e4c87ad4338e4885f5340e9ebf9f28b4f0906090211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 676ffec625ec287231995a533533c5f316140ae2a334ad2368c54bc2dd6b81e3 0.600000000000 1843776 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": 1355783, "vin": [ { "gen": { "height": 1355773 } } ], "vout": [ { "amount": 600000000, "target": { "key": "676ffec625ec287231995a533533c5f316140ae2a334ad2368c54bc2dd6b81e3" } } ], "extra": [ 1, 109, 63, 162, 61, 186, 200, 7, 61, 33, 0, 182, 87, 62, 76, 135, 173, 67, 56, 228, 136, 95, 83, 64, 233, 235, 249, 242, 139, 79, 9, 6, 9, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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