Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c6f8f794061fc9f77830970028e173e9fc5d008907e6b2f8d5b77b0ba2cad9f

Tx prefix hash: ed7411727fd67d8bee176b8bb3b368bd1fa5dda7557e6a3ae627eeac2ba0232b
Tx public key: c461f7b3324f647d678b83beeadf7dca7375e76686c725cb20b4bf04fa55f57c
Timestamp: 1725143288 Timestamp [UCT]: 2024-08-31 22:28:08 Age [y:d:h:m:s]: 00:053:00:02:55
Block: 1100190 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37946 RingCT/type: yes/0
Extra: 01c461f7b3324f647d678b83beeadf7dca7375e76686c725cb20b4bf04fa55f57c02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14fb5b1eb1fd77b13ef2ece98a27a18f1ad0a1b034e59129dadeff8bc457ed1b 0.600000000000 1576163 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": 1100200, "vin": [ { "gen": { "height": 1100190 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14fb5b1eb1fd77b13ef2ece98a27a18f1ad0a1b034e59129dadeff8bc457ed1b" } } ], "extra": [ 1, 196, 97, 247, 179, 50, 79, 100, 125, 103, 139, 131, 190, 234, 223, 125, 202, 115, 117, 231, 102, 134, 199, 37, 203, 32, 180, 191, 4, 250, 85, 245, 124, 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