Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2e7e63030611e37dbbde3bd8e713a014643f73e3ed2994832ae7be6cde121aa

Tx prefix hash: 39ffb1cd8394739da21e00b90939b331f1362d37971ad44e9b9b5c195761125c
Tx public key: 30823e02ebc3096fc97d238eb930e9cf980c456d39b27eefa71abf4f1e3ce199
Timestamp: 1730828017 Timestamp [UCT]: 2024-11-05 17:33:37 Age [y:d:h:m:s]: 00:149:13:07:23
Block: 1147239 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106712 RingCT/type: yes/0
Extra: 0130823e02ebc3096fc97d238eb930e9cf980c456d39b27eefa71abf4f1e3ce199021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 12140d6415e6552fcd21742a9fb5686d7bff9f2a4da2bc4f74fcae50eaf853f7 0.600000000000 1631934 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": 1147249, "vin": [ { "gen": { "height": 1147239 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12140d6415e6552fcd21742a9fb5686d7bff9f2a4da2bc4f74fcae50eaf853f7" } } ], "extra": [ 1, 48, 130, 62, 2, 235, 195, 9, 111, 201, 125, 35, 142, 185, 48, 233, 207, 152, 12, 69, 109, 57, 178, 126, 239, 167, 26, 191, 79, 30, 60, 225, 153, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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