Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ac719f253dd1e1c03f7d6c2a72ca4dd6e1248015b79252904d3bc30b7c7770f

Tx prefix hash: 2347864f10834fc8d9e3427fa16cdfe5c11afc893a9ae401326dc117d793b62b
Tx public key: 1749239d7d29718c25607b38cec878429fb8980a59a0143533682ae98a7a48ba
Timestamp: 1582106747 Timestamp [UCT]: 2020-02-19 10:05:47 Age [y:d:h:m:s]: 05:070:00:08:18
Block: 68072 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1203162 RingCT/type: yes/0
Extra: 011749239d7d29718c25607b38cec878429fb8980a59a0143533682ae98a7a48ba02110000000f4943cd9f000000000000000000

1 output(s) for total of 365.132097936000 dcy

stealth address amount amount idx
00: 6f228313ab51a9aaefde584aa2026e3d85d870e8e34ba7c2ade4bb956314ca80 365.132097936000 125430 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": 68082, "vin": [ { "gen": { "height": 68072 } } ], "vout": [ { "amount": 365132097936, "target": { "key": "6f228313ab51a9aaefde584aa2026e3d85d870e8e34ba7c2ade4bb956314ca80" } } ], "extra": [ 1, 23, 73, 35, 157, 125, 41, 113, 140, 37, 96, 123, 56, 206, 200, 120, 66, 159, 184, 152, 10, 89, 160, 20, 53, 51, 104, 42, 233, 138, 122, 72, 186, 2, 17, 0, 0, 0, 15, 73, 67, 205, 159, 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