Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93d5062a4ffc7f5d26bc50d7a795e929c7863f0c648fef50e4e6da0e02da377c

Tx prefix hash: 2f2020d25277871a274bb175084fb5d24ff7c2269769d26cdb15f76a252f91bf
Tx public key: 8b85d57afb553fea4baeb9da3143dfa7708232d37f3f44873a76f67ce9ceb1a7
Timestamp: 1722740630 Timestamp [UCT]: 2024-08-04 03:03:50 Age [y:d:h:m:s]: 00:245:02:22:47
Block: 1080281 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175064 RingCT/type: yes/0
Extra: 018b85d57afb553fea4baeb9da3143dfa7708232d37f3f44873a76f67ce9ceb1a702110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec4f4fa4bcc8ccf940549ff23f4ea3dc30bf3b0882506b81a535757577079ac0 0.600000000000 1553574 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": 1080291, "vin": [ { "gen": { "height": 1080281 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec4f4fa4bcc8ccf940549ff23f4ea3dc30bf3b0882506b81a535757577079ac0" } } ], "extra": [ 1, 139, 133, 213, 122, 251, 85, 63, 234, 75, 174, 185, 218, 49, 67, 223, 167, 112, 130, 50, 211, 127, 63, 68, 135, 58, 118, 246, 124, 233, 206, 177, 167, 2, 17, 0, 0, 0, 1, 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