Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f91463450d9c6c7412f1afff13a765b6dd3f1dab0d6fa7a41aa449395a25bac

Tx prefix hash: b7a690003416cdffdddee9441172bc001466a4c465800fe1bc5a9ac202f37e75
Tx public key: 39c52a5193afe579fb7a54b1e8a8b36f38dfdbc2108f7a5b784d5b072fdcff81
Timestamp: 1577003860 Timestamp [UCT]: 2019-12-22 08:37:40 Age [y:d:h:m:s]: 05:012:10:46:44
Block: 29554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1158521 RingCT/type: yes/0
Extra: 0139c52a5193afe579fb7a54b1e8a8b36f38dfdbc2108f7a5b784d5b072fdcff8102110000000e4ac5aa02000000000000000000

1 output(s) for total of 489.864753551000 dcy

stealth address amount amount idx
00: 3dbaa6313d260d6db28d09f7e4d43974fd6e508ee958f64d15c40e6373c8b311 489.864753551000 48628 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": 29564, "vin": [ { "gen": { "height": 29554 } } ], "vout": [ { "amount": 489864753551, "target": { "key": "3dbaa6313d260d6db28d09f7e4d43974fd6e508ee958f64d15c40e6373c8b311" } } ], "extra": [ 1, 57, 197, 42, 81, 147, 175, 229, 121, 251, 122, 84, 177, 232, 168, 179, 111, 56, 223, 219, 194, 16, 143, 122, 91, 120, 77, 91, 7, 47, 220, 255, 129, 2, 17, 0, 0, 0, 14, 74, 197, 170, 2, 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