Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fd3c2d377e97cb661395f2f7559036e44814307841a74e963271d7715b5ead9

Tx prefix hash: 6e89afa65d9a4c87d541e6fda93d79a0e902c7a0d275a7625478af265255c57d
Tx public key: bf4f7ed8043902bf6c8bc18d6d2e0a8709701bcf1fe1bc7b4e705005ee00dcc4
Timestamp: 1758630782 Timestamp [UCT]: 2025-09-23 12:33:02 Age [y:d:h:m:s]: 00:051:06:45:57
Block: 1374712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36714 RingCT/type: yes/0
Extra: 01bf4f7ed8043902bf6c8bc18d6d2e0a8709701bcf1fe1bc7b4e705005ee00dcc402110000000bad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a4b0459e574f368cc04bf1dad24b1fa7010a8e97bc713991407e4ba9bc37108 0.600000000000 1862797 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": 1374722, "vin": [ { "gen": { "height": 1374712 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a4b0459e574f368cc04bf1dad24b1fa7010a8e97bc713991407e4ba9bc37108" } } ], "extra": [ 1, 191, 79, 126, 216, 4, 57, 2, 191, 108, 139, 193, 141, 109, 46, 10, 135, 9, 112, 27, 207, 31, 225, 188, 123, 78, 112, 80, 5, 238, 0, 220, 196, 2, 17, 0, 0, 0, 11, 173, 121, 72, 208, 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