Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 029aa7f8d00dcaaf3dced981e886ff3f80131660515a0634d3bdba37c86cf96f

Tx prefix hash: 49d94f60d2c1a666884200aa7bd2fdf9a2b502e994d40a23cb4078cee523f795
Tx public key: d9e5d49349985059e6c4f1412dc61e1f0f7815fd67a15a4e107f424f931aec1a
Timestamp: 1750345385 Timestamp [UCT]: 2025-06-19 15:03:05 Age [y:d:h:m:s]: 00:155:08:56:34
Block: 1308441 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108853 RingCT/type: yes/0
Extra: 01d9e5d49349985059e6c4f1412dc61e1f0f7815fd67a15a4e107f424f931aec1a021100000003d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43e252e75c2b54592cde74fa06d47f98e0ed6e668eeda4d04c9abd0b17bf7677 0.600000000000 1796054 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": 1308451, "vin": [ { "gen": { "height": 1308441 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43e252e75c2b54592cde74fa06d47f98e0ed6e668eeda4d04c9abd0b17bf7677" } } ], "extra": [ 1, 217, 229, 212, 147, 73, 152, 80, 89, 230, 196, 241, 65, 45, 198, 30, 31, 15, 120, 21, 253, 103, 161, 90, 78, 16, 127, 66, 79, 147, 26, 236, 26, 2, 17, 0, 0, 0, 3, 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