Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef6fc28cb87604581bd10bffaa0c5b2db5b232ab8d27300a8f1bfcfed8101f2f

Tx prefix hash: 2e3e951b4251bd578b1104fc3d252b964da659c81335d3607c2786efe9a41b25
Tx public key: 1d15fdf8786a55d58066f2226549a767152aa2a81b0c8eedd3033dc61343bc1d
Timestamp: 1751326055 Timestamp [UCT]: 2025-06-30 23:27:35 Age [y:d:h:m:s]: 00:131:22:37:40
Block: 1316169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92488 RingCT/type: yes/0
Extra: 011d15fdf8786a55d58066f2226549a767152aa2a81b0c8eedd3033dc61343bc1d021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f21f68f200d279a31fedb2cd5ca9d40d082256e2148044b0505ad0631c9d8365 0.600000000000 1803826 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": 1316179, "vin": [ { "gen": { "height": 1316169 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f21f68f200d279a31fedb2cd5ca9d40d082256e2148044b0505ad0631c9d8365" } } ], "extra": [ 1, 29, 21, 253, 248, 120, 106, 85, 213, 128, 102, 242, 34, 101, 73, 167, 103, 21, 42, 162, 168, 27, 12, 142, 237, 211, 3, 61, 198, 19, 67, 188, 29, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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