Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c19a3047da3720c67f6586816db945444ff50bd1a89261d240e96bf92d64851f

Tx prefix hash: 7b7d692a9ca227cfbaf058f5aa0590e863bcbdf71d9e0d8053ec8f1d7a1b04be
Tx public key: 81aa9efe5cfcfab69c457705b9bf9a9677aa6efe4dcff2da988115601202f0b7
Timestamp: 1707721191 Timestamp [UCT]: 2024-02-12 06:59:51 Age [y:d:h:m:s]: 01:058:15:50:02
Block: 955751 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302971 RingCT/type: yes/0
Extra: 0181aa9efe5cfcfab69c457705b9bf9a9677aa6efe4dcff2da988115601202f0b702110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2225bce79a8b3c73d791d6a1ee587017f55c3e310675739d931f2dd99660339 0.600000000000 1415051 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": 955761, "vin": [ { "gen": { "height": 955751 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2225bce79a8b3c73d791d6a1ee587017f55c3e310675739d931f2dd99660339" } } ], "extra": [ 1, 129, 170, 158, 254, 92, 252, 250, 182, 156, 69, 119, 5, 185, 191, 154, 150, 119, 170, 110, 254, 77, 207, 242, 218, 152, 129, 21, 96, 18, 2, 240, 183, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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