Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa0d58b4948987528228f1cf390cfc76b68bf000632bc6fdb63119ad46a14d6a

Tx prefix hash: 7f5262e6ad227c40f61cde24b94a764e34e24e076443f3865dc4fef6aa7b43b5
Tx public key: ece857a64f82a4b4eb933f740983acc734f2f9332ad8b3a1a4fbab8216ef0326
Timestamp: 1674787248 Timestamp [UCT]: 2023-01-27 02:40:48 Age [y:d:h:m:s]: 02:031:18:05:30
Block: 683600 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 544298 RingCT/type: yes/0
Extra: 01ece857a64f82a4b4eb933f740983acc734f2f9332ad8b3a1a4fbab8216ef03260211000000015029cbac000000000000000000

1 output(s) for total of 3.333875377000 dcy

stealth address amount amount idx
00: a9828eda39f8641b89c3d359ced58ff90c0a0e6ff712e04cf410e25903b5ae9d 3.333875377000 1125795 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": 683610, "vin": [ { "gen": { "height": 683600 } } ], "vout": [ { "amount": 3333875377, "target": { "key": "a9828eda39f8641b89c3d359ced58ff90c0a0e6ff712e04cf410e25903b5ae9d" } } ], "extra": [ 1, 236, 232, 87, 166, 79, 130, 164, 180, 235, 147, 63, 116, 9, 131, 172, 199, 52, 242, 249, 51, 42, 216, 179, 161, 164, 251, 171, 130, 22, 239, 3, 38, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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