Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0f7e4153804cd239092d0a3196425c957f0fd705c3bf9cd2470ef0942700e92

Tx prefix hash: f4b798127f2cd47c062a5a9499c141d906e0cdb1b1a624f155f4bfc7ce980c16
Tx public key: 409ac2bff1555e477a0fbda3e83efc9eeda6ff777b64711518abf1ddff596fa3
Timestamp: 1576281805 Timestamp [UCT]: 2019-12-14 00:03:25 Age [y:d:h:m:s]: 05:082:22:19:02
Block: 26557 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1205693 RingCT/type: yes/0
Extra: 01409ac2bff1555e477a0fbda3e83efc9eeda6ff777b64711518abf1ddff596fa302110000000c9159db1e000000000000000000

1 output(s) for total of 501.194737155000 dcy

stealth address amount amount idx
00: 9456fd319e7a174fb736af9ff17f8df844b63d559e5a1eed6679f3dd2fee05d7 501.194737155000 44014 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": 26567, "vin": [ { "gen": { "height": 26557 } } ], "vout": [ { "amount": 501194737155, "target": { "key": "9456fd319e7a174fb736af9ff17f8df844b63d559e5a1eed6679f3dd2fee05d7" } } ], "extra": [ 1, 64, 154, 194, 191, 241, 85, 94, 71, 122, 15, 189, 163, 232, 62, 252, 158, 237, 166, 255, 119, 123, 100, 113, 21, 24, 171, 241, 221, 255, 89, 111, 163, 2, 17, 0, 0, 0, 12, 145, 89, 219, 30, 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