Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b2547429ed7e6fce73dcdf023caa555edeb9cb03cff074ae9f0f0213aea1132

Tx prefix hash: 7310cbca7e0981be7394e629c6a17f81765b75fa3205df98a85a86f7eb892e26
Tx public key: c35dbb8e7decdae44df6aca9f3a1e2b06985cf079b396c85ea1ad95ddcc8bd75
Timestamp: 1656900065 Timestamp [UCT]: 2022-07-04 02:01:05 Age [y:d:h:m:s]: 02:135:01:35:14
Block: 536143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 617832 RingCT/type: yes/0
Extra: 01c35dbb8e7decdae44df6aca9f3a1e2b06985cf079b396c85ea1ad95ddcc8bd750211000000125eb576c5000000000000000000

1 output(s) for total of 10.269181507000 dcy

stealth address amount amount idx
00: 470cfb29bbb9025a5c0905ecf4fedcfd4899435b1e639b6d5f42209b3b5f8aa7 10.269181507000 965844 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": 536153, "vin": [ { "gen": { "height": 536143 } } ], "vout": [ { "amount": 10269181507, "target": { "key": "470cfb29bbb9025a5c0905ecf4fedcfd4899435b1e639b6d5f42209b3b5f8aa7" } } ], "extra": [ 1, 195, 93, 187, 142, 125, 236, 218, 228, 77, 246, 172, 169, 243, 161, 226, 176, 105, 133, 207, 7, 155, 57, 108, 133, 234, 26, 217, 93, 220, 200, 189, 117, 2, 17, 0, 0, 0, 18, 94, 181, 118, 197, 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