Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5fd86c2be2f96a12d09864d9f2bd500707197e4303faaa4d453c2b47f550f78c

Tx prefix hash: 3e948d157df150ef0c17e2a288aac3b10e3290643b668b925986b06f6afeb1b4
Tx public key: b91835494fdbf85d078dcb4c1dbd7a5531429fe7a19004c85de31dd375476a7d
Timestamp: 1702844056 Timestamp [UCT]: 2023-12-17 20:14:16 Age [y:d:h:m:s]: 01:178:15:28:10
Block: 915321 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388792 RingCT/type: yes/0
Extra: 01b91835494fdbf85d078dcb4c1dbd7a5531429fe7a19004c85de31dd375476a7d02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e2fa9767256b44ae912bba26423f15dcbbfa60d35d06810a8b633c2dc97dfdb 0.600000000000 1372715 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": 915331, "vin": [ { "gen": { "height": 915321 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e2fa9767256b44ae912bba26423f15dcbbfa60d35d06810a8b633c2dc97dfdb" } } ], "extra": [ 1, 185, 24, 53, 73, 79, 219, 248, 93, 7, 141, 203, 76, 29, 189, 122, 85, 49, 66, 159, 231, 161, 144, 4, 200, 93, 227, 29, 211, 117, 71, 106, 125, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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