Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7ac6327855e6f10766e417df030aa1deb3dc6be3938d37c30121021c49c047c

Tx prefix hash: eb3e79e5c371a9387fbb0ecabb69e9be0e386a13e0d673e41a73f280a632268d
Tx public key: 2a0a3ae333b10fe06f271202acacbcc31800df5a2f7680c95bcc5c29a48a90bc
Timestamp: 1738028532 Timestamp [UCT]: 2025-01-28 01:42:12 Age [y:d:h:m:s]: 00:045:10:55:57
Block: 1206618 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32514 RingCT/type: yes/0
Extra: 012a0a3ae333b10fe06f271202acacbcc31800df5a2f7680c95bcc5c29a48a90bc0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4cccc98dd54134f63e6ab8ace181a1202ccd4ef40c24ae38e18dd6205f2b5660 0.600000000000 1693329 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": 1206628, "vin": [ { "gen": { "height": 1206618 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4cccc98dd54134f63e6ab8ace181a1202ccd4ef40c24ae38e18dd6205f2b5660" } } ], "extra": [ 1, 42, 10, 58, 227, 51, 177, 15, 224, 111, 39, 18, 2, 172, 172, 188, 195, 24, 0, 223, 90, 47, 118, 128, 201, 91, 204, 92, 41, 164, 138, 144, 188, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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