Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3abdf80d0367c67f43b60eb935a8dec227198df4aa9e159f273ab54dcf2c9392

Tx prefix hash: a6e6b83a8ce3059d2100499a8508d52bcfa8c1f407ac779ddb07e23c481ff3b0
Tx public key: 51fa8a10748deca4a3354612dfe1acd17baee17e00b445b0dd3d3b1b1381b433
Timestamp: 1728306440 Timestamp [UCT]: 2024-10-07 13:07:20 Age [y:d:h:m:s]: 00:193:05:12:56
Block: 1126426 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137893 RingCT/type: yes/0
Extra: 0151fa8a10748deca4a3354612dfe1acd17baee17e00b445b0dd3d3b1b1381b43302110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b25807ed03ea23d9bc3e22a864c3eed9151e26bef1ec91f500ffd9b289d8f44 0.600000000000 1609217 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": 1126436, "vin": [ { "gen": { "height": 1126426 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b25807ed03ea23d9bc3e22a864c3eed9151e26bef1ec91f500ffd9b289d8f44" } } ], "extra": [ 1, 81, 250, 138, 16, 116, 141, 236, 164, 163, 53, 70, 18, 223, 225, 172, 209, 123, 174, 225, 126, 0, 180, 69, 176, 221, 61, 59, 27, 19, 129, 180, 51, 2, 17, 0, 0, 0, 2, 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