Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27875dc1baa49c9703b7693f3dedfee64ca3772bb35792b7f4380652371b9835

Tx prefix hash: 3310ae2d30b6f62cf21a39883922f4b06c933cc884d8b15edb779a2a7742a9cb
Tx public key: 1279e129e760c7d173d2f6f473e0c7791fbf7b02bbf6555d4faf8e91ea4af947
Timestamp: 1602481139 Timestamp [UCT]: 2020-10-12 05:38:59 Age [y:d:h:m:s]: 04:231:04:09:13
Block: 140724 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1153396 RingCT/type: yes/0
Extra: 011279e129e760c7d173d2f6f473e0c7791fbf7b02bbf6555d4faf8e91ea4af94702110000018ff8cbd8e0000000000000000000

1 output(s) for total of 209.784083301000 dcy

stealth address amount amount idx
00: 8b1235ffc5e97fd5e717b1d86083efa806a83d446447921359bdba1ee13fb0f2 209.784083301000 233727 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": 140734, "vin": [ { "gen": { "height": 140724 } } ], "vout": [ { "amount": 209784083301, "target": { "key": "8b1235ffc5e97fd5e717b1d86083efa806a83d446447921359bdba1ee13fb0f2" } } ], "extra": [ 1, 18, 121, 225, 41, 231, 96, 199, 209, 115, 210, 246, 244, 115, 224, 199, 121, 31, 191, 123, 2, 187, 246, 85, 93, 79, 175, 142, 145, 234, 74, 249, 71, 2, 17, 0, 0, 1, 143, 248, 203, 216, 224, 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