Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 388f3bb307893fda942152b4ca9fde02ef346c292c569a13582096b92add1e82

Tx prefix hash: ca295e4369ea124a55acf34f2fb9e0dedc7067944d77ade89ac327b929b4cf98
Tx public key: abe4db7f5c890ac0ac670c39817f82a3d1a65dc83c7afa0a7f3c442b48f3a296
Timestamp: 1714341178 Timestamp [UCT]: 2024-04-28 21:52:58 Age [y:d:h:m:s]: 00:256:15:34:08
Block: 1010636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183700 RingCT/type: yes/0
Extra: 01abe4db7f5c890ac0ac670c39817f82a3d1a65dc83c7afa0a7f3c442b48f3a29602110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0805e1dc749c28ee7769f9954b96bd3e8e3f2eafa00b4dda5e1487101f23354e 0.600000000000 1472650 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": 1010646, "vin": [ { "gen": { "height": 1010636 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0805e1dc749c28ee7769f9954b96bd3e8e3f2eafa00b4dda5e1487101f23354e" } } ], "extra": [ 1, 171, 228, 219, 127, 92, 137, 10, 192, 172, 103, 12, 57, 129, 127, 130, 163, 209, 166, 93, 200, 60, 122, 250, 10, 127, 60, 68, 43, 72, 243, 162, 150, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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