Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f1617d2c7378aa38cba62e99f5a09079ad480d5695f3921e3e05e3525294c06

Tx prefix hash: 1337295e792c9467e3eadf754a877f3d8d521182e5167c7cd4e1914b68519d25
Tx public key: 951bb0479c74c53d671a72cd491af3746b84f89712b6016144d8f2a0d35b2f34
Timestamp: 1726803431 Timestamp [UCT]: 2024-09-20 03:37:11 Age [y:d:h:m:s]: 00:189:09:59:53
Block: 1113965 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135183 RingCT/type: yes/0
Extra: 01951bb0479c74c53d671a72cd491af3746b84f89712b6016144d8f2a0d35b2f34021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1575ace4cec542d563176a0254e11c1fa4f5c70413b2bc12e26493c5aa4a96cc 0.600000000000 1593762 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": 1113975, "vin": [ { "gen": { "height": 1113965 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1575ace4cec542d563176a0254e11c1fa4f5c70413b2bc12e26493c5aa4a96cc" } } ], "extra": [ 1, 149, 27, 176, 71, 156, 116, 197, 61, 103, 26, 114, 205, 73, 26, 243, 116, 107, 132, 248, 151, 18, 182, 1, 97, 68, 216, 242, 160, 211, 91, 47, 52, 2, 17, 0, 0, 0, 2, 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