Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 259cc960ef118f285b40aec07d27eafc45965424fbc9f4c704986051776eccd0

Tx prefix hash: c5029df636e1e2a369d10b9776557ddf56039a72e4f824dae61dfa91438a2bfe
Tx public key: cea7bc7250e8f6c386b5cb1f210ea65a83c79de7c9b1c196f9b885ff944502fa
Timestamp: 1751285196 Timestamp [UCT]: 2025-06-30 12:06:36 Age [y:d:h:m:s]: 00:137:12:40:06
Block: 1315831 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96481 RingCT/type: yes/0
Extra: 01cea7bc7250e8f6c386b5cb1f210ea65a83c79de7c9b1c196f9b885ff944502fa021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36e8f922c4bcd8be6e609f1f97b5864920716e1698f8b93de386a6f08e9971b2 0.600000000000 1803488 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": 1315841, "vin": [ { "gen": { "height": 1315831 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36e8f922c4bcd8be6e609f1f97b5864920716e1698f8b93de386a6f08e9971b2" } } ], "extra": [ 1, 206, 167, 188, 114, 80, 232, 246, 195, 134, 181, 203, 31, 33, 14, 166, 90, 131, 199, 157, 231, 201, 177, 193, 150, 249, 184, 133, 255, 148, 69, 2, 250, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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