Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b38b3f0b0b59a414b06ce319d966a925b2034cc53b2e8d394d51922389f3711

Tx prefix hash: 713a26f6202543f5fcccbb2f7e33e9b72c014d92bc0a93046c1b6baef6b5e969
Tx public key: ae81232b045f26864ef5f547bbf10c545c04a6c96050cbd17b6ff5a522427113
Timestamp: 1727206730 Timestamp [UCT]: 2024-09-24 19:38:50 Age [y:d:h:m:s]: 00:119:21:25:46
Block: 1117307 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85677 RingCT/type: yes/0
Extra: 01ae81232b045f26864ef5f547bbf10c545c04a6c96050cbd17b6ff5a522427113021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5396058a60d06a897c581feaac1ca51bcacbc9b5c1a850267b38e90a5606942 0.600000000000 1598096 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": 1117317, "vin": [ { "gen": { "height": 1117307 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5396058a60d06a897c581feaac1ca51bcacbc9b5c1a850267b38e90a5606942" } } ], "extra": [ 1, 174, 129, 35, 43, 4, 95, 38, 134, 78, 245, 245, 71, 187, 241, 12, 84, 92, 4, 166, 201, 96, 80, 203, 209, 123, 111, 245, 165, 34, 66, 113, 19, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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