Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c7aee6ec425433bc9ec82c03cc203175a5e91dc7d9239153a5f5f77829c4da1

Tx prefix hash: b50639e7f583a9907a0c3e640dc52d75adddbb3676f4ebe29184b6b900dc25a3
Tx public key: 1430aa04da3e2f8c967148036514ffa48e21c23eb49fd7673d9ec5f708d8ec0a
Timestamp: 1751157610 Timestamp [UCT]: 2025-06-29 00:40:10 Age [y:d:h:m:s]: 00:193:14:59:48
Block: 1314874 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136545 RingCT/type: yes/0
Extra: 011430aa04da3e2f8c967148036514ffa48e21c23eb49fd7673d9ec5f708d8ec0a021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 501ae32c506be5f7a12f6221d3fb3c7187697d7517ce93fbc720db564baf9384 0.600000000000 1802527 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": 1314884, "vin": [ { "gen": { "height": 1314874 } } ], "vout": [ { "amount": 600000000, "target": { "key": "501ae32c506be5f7a12f6221d3fb3c7187697d7517ce93fbc720db564baf9384" } } ], "extra": [ 1, 20, 48, 170, 4, 218, 62, 47, 140, 150, 113, 72, 3, 101, 20, 255, 164, 142, 33, 194, 62, 180, 159, 215, 103, 61, 158, 197, 247, 8, 216, 236, 10, 2, 17, 0, 0, 0, 2, 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