Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ae80ad71b23975cdd2f72b7496edc258bd9c1f6b397694fe7a22a721caff697

Tx prefix hash: 32fe8ff2ecbd458ed184e890b896c99556fb9ebcf62945d80159cc97b18b95a8
Tx public key: 24dcf1d986f8b2a99b4c14590fbc4814573f786fc885d84e3c9508c6a2d1b8a6
Timestamp: 1710631902 Timestamp [UCT]: 2024-03-16 23:31:42 Age [y:d:h:m:s]: 00:313:21:50:09
Block: 979909 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224627 RingCT/type: yes/0
Extra: 0124dcf1d986f8b2a99b4c14590fbc4814573f786fc885d84e3c9508c6a2d1b8a602110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6612fef0c04d141965148a21d6e4666c41fe32c99914de5fa19e422b877926ba 0.600000000000 1439964 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": 979919, "vin": [ { "gen": { "height": 979909 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6612fef0c04d141965148a21d6e4666c41fe32c99914de5fa19e422b877926ba" } } ], "extra": [ 1, 36, 220, 241, 217, 134, 248, 178, 169, 155, 76, 20, 89, 15, 188, 72, 20, 87, 63, 120, 111, 200, 133, 216, 78, 60, 149, 8, 198, 162, 209, 184, 166, 2, 17, 0, 0, 0, 1, 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