Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f45363d14defdd762ce44b4e055608a774ceaed2e771b16d0fccd918794a1085

Tx prefix hash: e96cbee9ee40c9bd2ec33004ce344f5ba05dd66c0810867e202d61958cc7273f
Tx public key: a333ae701eeb7bd5ee7cc63f14b4f4c13f025e1dfa23b599366579fb172c3f0f
Timestamp: 1694272601 Timestamp [UCT]: 2023-09-09 15:16:41 Age [y:d:h:m:s]: 01:230:05:40:29
Block: 844443 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 425672 RingCT/type: yes/0
Extra: 01a333ae701eeb7bd5ee7cc63f14b4f4c13f025e1dfa23b599366579fb172c3f0f021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.977299410000 dcy

stealth address amount amount idx
00: 0d344a69df12917f6d0d64f6670c6149c0d95a5b5d902d8005bcddbf2019ee4e 0.977299410000 1297751 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": 844453, "vin": [ { "gen": { "height": 844443 } } ], "vout": [ { "amount": 977299410, "target": { "key": "0d344a69df12917f6d0d64f6670c6149c0d95a5b5d902d8005bcddbf2019ee4e" } } ], "extra": [ 1, 163, 51, 174, 112, 30, 235, 123, 213, 238, 124, 198, 63, 20, 180, 244, 193, 63, 2, 94, 29, 250, 35, 181, 153, 54, 101, 121, 251, 23, 44, 63, 15, 2, 17, 0, 0, 0, 7, 230, 210, 127, 156, 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