Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e066b5490e62ee31dcecf27751d8f1b290a6ce364be55610560bde6a75ae3ed

Tx prefix hash: f8b7f168ef1fd14bcd09edb7d9210a051bb08fdffcd2796be5db51f4142e9903
Tx public key: fb9b08033e755e9f2371d8f1dcb0ef3479cd602345f034fc46eaf808da21cb93
Timestamp: 1717338423 Timestamp [UCT]: 2024-06-02 14:27:03 Age [y:d:h:m:s]: 00:305:08:53:40
Block: 1035500 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218228 RingCT/type: yes/0
Extra: 01fb9b08033e755e9f2371d8f1dcb0ef3479cd602345f034fc46eaf808da21cb9302110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 77b941f12d60974afa79d3f7bcd9a65f73352483ef1dd37c4573c09a3d9e2f08 0.600000000000 1504021 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": 1035510, "vin": [ { "gen": { "height": 1035500 } } ], "vout": [ { "amount": 600000000, "target": { "key": "77b941f12d60974afa79d3f7bcd9a65f73352483ef1dd37c4573c09a3d9e2f08" } } ], "extra": [ 1, 251, 155, 8, 3, 62, 117, 94, 159, 35, 113, 216, 241, 220, 176, 239, 52, 121, 205, 96, 35, 69, 240, 52, 252, 70, 234, 248, 8, 218, 33, 203, 147, 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