Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed2728c05c57a4e4c53dbfe9d137ce7af20491c5645cc3a664a197f7c638ac1e

Tx prefix hash: 9f6c8e4a2251c8338f43ceb9d7ecda8d1bcf966729d674547d80bf51bf510422
Tx public key: b254323eae3087ea633b9bbd09657d66e1afad0425d1832976c81df83a7a1c8e
Timestamp: 1725160083 Timestamp [UCT]: 2024-09-01 03:08:03 Age [y:d:h:m:s]: 00:209:22:33:26
Block: 1100331 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149900 RingCT/type: yes/0
Extra: 01b254323eae3087ea633b9bbd09657d66e1afad0425d1832976c81df83a7a1c8e021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7aa607b34c04aa8d34c2c1a52d6e01d6961c3b0c9afe8cf5c58c5268407ea7f6 0.600000000000 1576306 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": 1100341, "vin": [ { "gen": { "height": 1100331 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7aa607b34c04aa8d34c2c1a52d6e01d6961c3b0c9afe8cf5c58c5268407ea7f6" } } ], "extra": [ 1, 178, 84, 50, 62, 174, 48, 135, 234, 99, 59, 155, 189, 9, 101, 125, 102, 225, 175, 173, 4, 37, 209, 131, 41, 118, 200, 29, 248, 58, 122, 28, 142, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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