Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b46da3a00a7d19bb200aa503a223632db8287dca37fe303a960918e64d976330

Tx prefix hash: 0541c687b9bbf8891dbbb4c4773fc28a00b57a33d3aefcd68f80209be18f5c4c
Tx public key: 2461b6b8b0e254046e8d0cdbfb8d3fbca2569a310dd1af65ecc1b843159baebd
Timestamp: 1751215924 Timestamp [UCT]: 2025-06-29 16:52:04 Age [y:d:h:m:s]: 00:151:16:38:20
Block: 1315303 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106580 RingCT/type: yes/0
Extra: 012461b6b8b0e254046e8d0cdbfb8d3fbca2569a310dd1af65ecc1b843159baebd021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f829637c3c4363f865725cf18e18bb9e77050895bbabe4a0c331cb6f5388d89 0.600000000000 1802956 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": 1315313, "vin": [ { "gen": { "height": 1315303 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f829637c3c4363f865725cf18e18bb9e77050895bbabe4a0c331cb6f5388d89" } } ], "extra": [ 1, 36, 97, 182, 184, 176, 226, 84, 4, 110, 141, 12, 219, 251, 141, 63, 188, 162, 86, 154, 49, 13, 209, 175, 101, 236, 193, 184, 67, 21, 155, 174, 189, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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