Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c32e98979b8d5d0ecfabd95ac0475ae00ba70aee041f2ca9694ddc67a2d96fca

Tx prefix hash: 8a28d241fdcd1fd6110a2dd55d5f8b3846efd0c0c382fa35f2b825b1a598ab97
Tx public key: b74e757b090096c7743fb9c34438ce647c62b03644f1e3441636f28675261081
Timestamp: 1625513321 Timestamp [UCT]: 2021-07-05 19:28:41 Age [y:d:h:m:s]: 03:216:05:17:43
Block: 288785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 924215 RingCT/type: yes/0
Extra: 01b74e757b090096c7743fb9c34438ce647c62b03644f1e3441636f2867526108102110000000a4b22f71d000000000000000000

1 output(s) for total of 67.785362293000 dcy

stealth address amount amount idx
00: 5884e439d3d55e5f39cf5c5020a4ae3ce48da4638f7dd696203dabe9a6e1d732 67.785362293000 604964 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": 288795, "vin": [ { "gen": { "height": 288785 } } ], "vout": [ { "amount": 67785362293, "target": { "key": "5884e439d3d55e5f39cf5c5020a4ae3ce48da4638f7dd696203dabe9a6e1d732" } } ], "extra": [ 1, 183, 78, 117, 123, 9, 0, 150, 199, 116, 63, 185, 195, 68, 56, 206, 100, 124, 98, 176, 54, 68, 241, 227, 68, 22, 54, 242, 134, 117, 38, 16, 129, 2, 17, 0, 0, 0, 10, 75, 34, 247, 29, 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