Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4fd51f01cb96c1682d446effa83517e225fbe79ea30215b33fe91b2236052c0

Tx prefix hash: 01ed56f9be7b9d02a6c5ff62aa05950ea23914eefae43d71290bb35320b59a38
Tx public key: 5d8fdf24ea8f7614c6f059fdb8f264bfdf49b659035f559bdc50c2850e3508db
Timestamp: 1728512968 Timestamp [UCT]: 2024-10-09 22:29:28 Age [y:d:h:m:s]: 00:161:17:43:14
Block: 1128125 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115403 RingCT/type: yes/0
Extra: 015d8fdf24ea8f7614c6f059fdb8f264bfdf49b659035f559bdc50c2850e3508db02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0da4781dcc40d1df1e309507d0cf3d0402b466ccef371a76463585e74ff3c0ca 0.600000000000 1610942 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": 1128135, "vin": [ { "gen": { "height": 1128125 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0da4781dcc40d1df1e309507d0cf3d0402b466ccef371a76463585e74ff3c0ca" } } ], "extra": [ 1, 93, 143, 223, 36, 234, 143, 118, 20, 198, 240, 89, 253, 184, 242, 100, 191, 223, 73, 182, 89, 3, 95, 85, 155, 220, 80, 194, 133, 14, 53, 8, 219, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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