Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 827a32e78828c356cc0486338e120f121a4bf163a44fcdb67738411356e01a23

Tx prefix hash: de6f8221181e723f9a90518389c6433b9021f934a29f949ea47d139421acf0d5
Tx public key: 2aa6b3a4534f5b36bd3c7dd762d763d00c72c361c374d1c9fc3bbaad4d3880b8
Timestamp: 1706946774 Timestamp [UCT]: 2024-02-03 07:52:54 Age [y:d:h:m:s]: 01:135:18:42:03
Block: 949321 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358035 RingCT/type: yes/0
Extra: 012aa6b3a4534f5b36bd3c7dd762d763d00c72c361c374d1c9fc3bbaad4d3880b802110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c84c4f430812a2081c894864afc7f050593e28980b311b3d5e64158d6d86ee63 0.600000000000 1407845 of 15

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": 949331, "vin": [ { "gen": { "height": 949321 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c84c4f430812a2081c894864afc7f050593e28980b311b3d5e64158d6d86ee63" } } ], "extra": [ 1, 42, 166, 179, 164, 83, 79, 91, 54, 189, 60, 125, 215, 98, 215, 99, 208, 12, 114, 195, 97, 195, 116, 209, 201, 252, 59, 186, 173, 77, 56, 128, 184, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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