Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9cb6799b0437092a0e148cb67c8b403b3e2e30b70bb39b3c74e7b5bb444690f1

Tx prefix hash: 06ac85687b1c57ea188e58905d15406d68ad0fa1fa111c7f80913f777c51e0e3
Tx public key: 4bcfa1c5882e15f1d3eb73ebeed29f8fa455b68612ba66a896b29acd4c9dc33d
Timestamp: 1675134615 Timestamp [UCT]: 2023-01-31 03:10:15 Age [y:d:h:m:s]: 01:347:10:43:57
Block: 686474 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 509307 RingCT/type: yes/0
Extra: 014bcfa1c5882e15f1d3eb73ebeed29f8fa455b68612ba66a896b29acd4c9dc33d0211000000015029cbac000000000000000000

1 output(s) for total of 3.261569237000 dcy

stealth address amount amount idx
00: 3bdd1e5b15723b08258afee061661ed1bf82177850836da552158fca705dc74d 3.261569237000 1128967 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": 686484, "vin": [ { "gen": { "height": 686474 } } ], "vout": [ { "amount": 3261569237, "target": { "key": "3bdd1e5b15723b08258afee061661ed1bf82177850836da552158fca705dc74d" } } ], "extra": [ 1, 75, 207, 161, 197, 136, 46, 21, 241, 211, 235, 115, 235, 238, 210, 159, 143, 164, 85, 182, 134, 18, 186, 102, 168, 150, 178, 154, 205, 76, 157, 195, 61, 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