Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe18224dae721fe1f6a4b29ee85bf14305a040f876af45f7804640182703c861

Tx prefix hash: eb4e40e1d083ad0cbf1eb6fee4db503a7cccbf16960f985cf6e7cd9963b5d43a
Tx public key: 92d2f51b8c0ec852b52bf3301fedbecc3ed4092cf81276d8e06af58112a8dad7
Timestamp: 1717693320 Timestamp [UCT]: 2024-06-06 17:02:00 Age [y:d:h:m:s]: 00:344:12:29:20
Block: 1038431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246242 RingCT/type: yes/0
Extra: 0192d2f51b8c0ec852b52bf3301fedbecc3ed4092cf81276d8e06af58112a8dad702110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a222922de8aae2c6ea21b2964cf33637a57f2359d5b4a9ca843a8fdd95aad24 0.600000000000 1506992 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": 1038441, "vin": [ { "gen": { "height": 1038431 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a222922de8aae2c6ea21b2964cf33637a57f2359d5b4a9ca843a8fdd95aad24" } } ], "extra": [ 1, 146, 210, 245, 27, 140, 14, 200, 82, 181, 43, 243, 48, 31, 237, 190, 204, 62, 212, 9, 44, 248, 18, 118, 216, 224, 106, 245, 129, 18, 168, 218, 215, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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