Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a6f999a828677094fffb1b2cc028756c704d6960924c70f5af3e1b51524d8a9

Tx prefix hash: bc35086a477fa71e69ab2ad458d1d6e80f2036a4c40f96a84f800ab279cc33fc
Tx public key: 9b170b8784dd8911e979cd0f172b72fb566a7bfd2646ae00a7198ab2f6293f45
Timestamp: 1701041877 Timestamp [UCT]: 2023-11-26 23:37:57 Age [y:d:h:m:s]: 01:054:03:30:22
Block: 900377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300057 RingCT/type: yes/0
Extra: 019b170b8784dd8911e979cd0f172b72fb566a7bfd2646ae00a7198ab2f6293f450211000000024b8f5122000000000000000000

1 output(s) for total of 0.637789283000 dcy

stealth address amount amount idx
00: 673dab03f86ed1af6b2761470b5ff0732f62a3d1befdce46c5f0bc691419dfff 0.637789283000 1356878 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": 900387, "vin": [ { "gen": { "height": 900377 } } ], "vout": [ { "amount": 637789283, "target": { "key": "673dab03f86ed1af6b2761470b5ff0732f62a3d1befdce46c5f0bc691419dfff" } } ], "extra": [ 1, 155, 23, 11, 135, 132, 221, 137, 17, 233, 121, 205, 15, 23, 43, 114, 251, 86, 106, 123, 253, 38, 70, 174, 0, 167, 25, 138, 178, 246, 41, 63, 69, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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