Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77eea745896176dbf7e1ee56d94df744401fb2eda115f065613360b054c7e5d0

Tx prefix hash: ade6d37a39c6e1619a64b231cea46f4864c1ad38091414c15e70c73fcb79a755
Tx public key: f503a795db8eaea10122aec47523063c9b35f9f8bbe972e4fb25c9624466ab09
Timestamp: 1730862565 Timestamp [UCT]: 2024-11-06 03:09:25 Age [y:d:h:m:s]: 00:163:09:05:17
Block: 1147517 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116618 RingCT/type: yes/0
Extra: 01f503a795db8eaea10122aec47523063c9b35f9f8bbe972e4fb25c9624466ab09021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1dc076b3063ddc785c072c802478e2e4e508d96e726eebe2cb10572217352b5 0.600000000000 1632216 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": 1147527, "vin": [ { "gen": { "height": 1147517 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1dc076b3063ddc785c072c802478e2e4e508d96e726eebe2cb10572217352b5" } } ], "extra": [ 1, 245, 3, 167, 149, 219, 142, 174, 161, 1, 34, 174, 196, 117, 35, 6, 60, 155, 53, 249, 248, 187, 233, 114, 228, 251, 37, 201, 98, 68, 102, 171, 9, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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