Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2561fde5832f4ab30c307f9fa77e42ee3a1e08b8379938606028e9eb03ee41e

Tx prefix hash: f59c832b008fbe39bb0df8608025823280c534f6ea181b02b4d0b57d8ba5cbc8
Tx public key: e815dd2d1ca409a86d3b44058ecfafbdb2ccacbe54750246684c3de8d8e918a5
Timestamp: 1699955371 Timestamp [UCT]: 2023-11-14 09:49:31 Age [y:d:h:m:s]: 01:144:21:07:53
Block: 891377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364724 RingCT/type: yes/0
Extra: 01e815dd2d1ca409a86d3b44058ecfafbdb2ccacbe54750246684c3de8d8e918a502110000000275e3f0e9000000000000000000

1 output(s) for total of 0.683121520000 dcy

stealth address amount amount idx
00: 7ab14e8ca3c8a1e04c13d0f89e5c07e5286c9e28fa1a391be682a3737ea8b2e3 0.683121520000 1347420 of 0

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": 891387, "vin": [ { "gen": { "height": 891377 } } ], "vout": [ { "amount": 683121520, "target": { "key": "7ab14e8ca3c8a1e04c13d0f89e5c07e5286c9e28fa1a391be682a3737ea8b2e3" } } ], "extra": [ 1, 232, 21, 221, 45, 28, 164, 9, 168, 109, 59, 68, 5, 142, 207, 175, 189, 178, 204, 172, 190, 84, 117, 2, 70, 104, 76, 61, 232, 216, 233, 24, 165, 2, 17, 0, 0, 0, 2, 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