Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79dc8492cd0bcd6e8e7cbfb5b22878f0f3b1428ea08c2bafab9d853f80c19718

Tx prefix hash: 3e8f21697dabb182918d77e1bbeec6a50d59c248d02ae4516136d391890bc45c
Tx public key: 11093cb733b4fd9da4fc9675f26da2deb8939f1e9b322620ef9ed0f2b29b44bd
Timestamp: 1707394611 Timestamp [UCT]: 2024-02-08 12:16:51 Age [y:d:h:m:s]: 01:086:01:29:53
Block: 953041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322579 RingCT/type: yes/0
Extra: 0111093cb733b4fd9da4fc9675f26da2deb8939f1e9b322620ef9ed0f2b29b44bd02110000000a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: feca9605eb9c0a559ce8bf260bbcd89d13d10ca49a82aa61f68ce4f9c83154ca 0.600000000000 1412201 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": 953051, "vin": [ { "gen": { "height": 953041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "feca9605eb9c0a559ce8bf260bbcd89d13d10ca49a82aa61f68ce4f9c83154ca" } } ], "extra": [ 1, 17, 9, 60, 183, 51, 180, 253, 157, 164, 252, 150, 117, 242, 109, 162, 222, 184, 147, 159, 30, 155, 50, 38, 32, 239, 158, 208, 242, 178, 155, 68, 189, 2, 17, 0, 0, 0, 10, 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