Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c7179558630d203c5432ee3997d70a5d8edd694097cf30d509ec09e6e584d77

Tx prefix hash: 3fdf7ceda9c136bddf0f1c39e38eca7d1c9f27e2b93d3f50afb98d12157daaea
Tx public key: 8c01199e5bdc538a74d68427fae7018bbf5722bbe3c9f9165f6543d0d4e74faf
Timestamp: 1582567639 Timestamp [UCT]: 2020-02-24 18:07:19 Age [y:d:h:m:s]: 04:279:18:12:38
Block: 71656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1092609 RingCT/type: yes/0
Extra: 018c01199e5bdc538a74d68427fae7018bbf5722bbe3c9f9165f6543d0d4e74faf0211000000038a2ee0d9000000000000000000

1 output(s) for total of 355.301645487000 dcy

stealth address amount amount idx
00: 5f4b661bc8f24b764d3b854d8c24c0e4fa6c5cb48b2e1e4a87b2b60bfeb00ffd 355.301645487000 132385 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": 71666, "vin": [ { "gen": { "height": 71656 } } ], "vout": [ { "amount": 355301645487, "target": { "key": "5f4b661bc8f24b764d3b854d8c24c0e4fa6c5cb48b2e1e4a87b2b60bfeb00ffd" } } ], "extra": [ 1, 140, 1, 25, 158, 91, 220, 83, 138, 116, 214, 132, 39, 250, 231, 1, 139, 191, 87, 34, 187, 227, 201, 249, 22, 95, 101, 67, 208, 212, 231, 79, 175, 2, 17, 0, 0, 0, 3, 138, 46, 224, 217, 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