Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ebd774c2d54de039f00b597056a8d678eee5f4830a1efbbd61377e58a802f881

Tx prefix hash: fc17f24c3cd01cee1475a155a80c1b4b058dadec56cced279680ae16e5751f5d
Tx public key: bfed57fc8a9f483bea423e6af39b726dea438725e829a9b35234974ee749e8e1
Timestamp: 1717618914 Timestamp [UCT]: 2024-06-05 20:21:54 Age [y:d:h:m:s]: 00:305:09:28:43
Block: 1037804 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218255 RingCT/type: yes/0
Extra: 01bfed57fc8a9f483bea423e6af39b726dea438725e829a9b35234974ee749e8e1021100000002d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9814b4f28cd852c439d2072e0a65fab3b4daf6dc3500c89896c956a5b7ab1a1 0.600000000000 1506361 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": 1037814, "vin": [ { "gen": { "height": 1037804 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9814b4f28cd852c439d2072e0a65fab3b4daf6dc3500c89896c956a5b7ab1a1" } } ], "extra": [ 1, 191, 237, 87, 252, 138, 159, 72, 59, 234, 66, 62, 106, 243, 155, 114, 109, 234, 67, 135, 37, 232, 41, 169, 179, 82, 52, 151, 78, 231, 73, 232, 225, 2, 17, 0, 0, 0, 2, 215, 73, 245, 17, 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