Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ea60e97ae5cb1c0857f9b7e8e2003e71b9c12939e4fb0609605624907c221db

Tx prefix hash: f0bafe53e8b26ed98e8eef6d70e6714a7fd63698fb478527195fbf13e62f9836
Tx public key: 0181629e6e8b583aaba9f1c656c9802cb6b234f190a0b3bccb78afaf391f1af2
Timestamp: 1657665721 Timestamp [UCT]: 2022-07-12 22:42:01 Age [y:d:h:m:s]: 03:111:07:01:51
Block: 542472 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 859262 RingCT/type: yes/0
Extra: 010181629e6e8b583aaba9f1c656c9802cb6b234f190a0b3bccb78afaf391f1af202110000000633af99f4000000000000000000

1 output(s) for total of 9.785098831000 dcy

stealth address amount amount idx
00: b4bde80a11a801f0132f261d8f31c53b1d13713b4bfefd4bd56aac4d9b7978a2 9.785098831000 973039 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": 542482, "vin": [ { "gen": { "height": 542472 } } ], "vout": [ { "amount": 9785098831, "target": { "key": "b4bde80a11a801f0132f261d8f31c53b1d13713b4bfefd4bd56aac4d9b7978a2" } } ], "extra": [ 1, 1, 129, 98, 158, 110, 139, 88, 58, 171, 169, 241, 198, 86, 201, 128, 44, 182, 178, 52, 241, 144, 160, 179, 188, 203, 120, 175, 175, 57, 31, 26, 242, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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