Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67927453a068853b2f7ea58a19c356a562a9707c3cd3242acce5480ba62b916a

Tx prefix hash: b76a9a55daf0f060035bca845d896358a0a8d87c0e06d3d1226a62ca4d417f9d
Tx public key: aba1b1e09876aa6b8853ce0ebd91afa32a1bdbff4081461498aa4b60673ff3e2
Timestamp: 1744894101 Timestamp [UCT]: 2025-04-17 12:48:21 Age [y:d:h:m:s]: 00:019:12:11:48
Block: 1263426 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13964 RingCT/type: yes/0
Extra: 01aba1b1e09876aa6b8853ce0ebd91afa32a1bdbff4081461498aa4b60673ff3e20211000000046c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f825fc0c0655b4dc4c20beed149a2eb8ff8b4573401fa150201453524b36f913 0.600000000000 1750617 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": 1263436, "vin": [ { "gen": { "height": 1263426 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f825fc0c0655b4dc4c20beed149a2eb8ff8b4573401fa150201453524b36f913" } } ], "extra": [ 1, 171, 161, 177, 224, 152, 118, 170, 107, 136, 83, 206, 14, 189, 145, 175, 163, 42, 27, 219, 255, 64, 129, 70, 20, 152, 170, 75, 96, 103, 63, 243, 226, 2, 17, 0, 0, 0, 4, 108, 152, 170, 61, 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